Skip to content

Documentation on reproducing BUCK CI failures #14529

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Draft
wants to merge 1 commit into
base: main
Choose a base branch
from
Draft

Documentation on reproducing BUCK CI failures #14529

wants to merge 1 commit into from

Conversation

@mergennachin
Copy link
Contributor

@mergennachin mergennachin commented Sep 23, 2025 •
edited
Loading

I found having resolve_buck.py script helpful to reproduce buck tests locally.

I know @swolchok wanted to delete, but how about having it in our codebase, but actually use it in our CI?

@pytorch-bot
Copy link

pytorch-bot bot commented Sep 23, 2025 •
edited
Loading

🔗 Helpful Links

🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/executorch/14529

Note: Links to docs will display an error until the docs builds have been completed.

❌ 92 New Failures, 138 Cancelled Jobs

As of commit c5e5361 with merge base 95888a4 (image):

NEW FAILURES - The following jobs have failed:

CANCELLED JOBS - The following jobs were cancelled. Please retry:

This comment was automatically generated by Dr. CI and updates every 15 minutes.

@meta-cla meta-cla bot added the CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed. label Sep 23, 2025
@github-actions
Copy link

This PR needs a release notes: label

If your change should be included in the release notes (i.e. would users of this library care about this change?), please use a label starting with release notes:. This helps us keep track and include your important work in the next release notes.

To add a label, you can comment to pytorchbot, for example
@pytorchbot label "release notes: none"

For more information, see
https://github.com/pytorch/pytorch/wiki/PyTorch-AutoLabel-Bot#why-categorize-for-release-notes-and-how-does-it-work.

@mergennachin mergennachin force-pushed the call_resolve_buck_in_ci branch 2 times, most recently from 22d42e9 to 5aa2a63 Compare September 23, 2025 22:06
@mergennachin mergennachin marked this pull request as draft September 23, 2025 22:21
@mergennachin mergennachin force-pushed the call_resolve_buck_in_ci branch from 5aa2a63 to 9f34786 Compare September 23, 2025 22:35
@mergennachin mergennachin force-pushed the call_resolve_buck_in_ci branch from 9f34786 to c5e5361 Compare September 23, 2025 22:39
swolchok
swolchok reviewed Sep 26, 2025
View reviewed changes
CONTRIBUTING.md
all-green commit.

### BUCK tests
In addition to CMake, we run `buck` tests in our CI pipeline to ensure continued integration with certain customers. We recognize that `buck` is not a widely used build system and may not be installed on your local machine. If you encounter a failure in the `buck` CI and wish to reproduce it locally, follow these steps:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

buck is not a widely used build system and may not be installed on your local machine

even if you do have buck2 installed, you need the exact version that goes with the version of the buck2 prelude we're using

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@swolchok swolchok swolchok left review comments

At least 1 approving review is required to merge this pull request.

Assignees

No one assigned

Labels

CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed.

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@mergennachin @swolchok